Granting reservation for access to a storage drive

ABSTRACT

A method includes, responsive to receiving a modified first reservation command from a storage controller, identifying, by a storage drive, a first range of storage based on a first range identifier of the modified reservation command. The method also includes granting, by the storage drive, a reservation for access to the storage drive on behalf of a first host controller by associating the reservation for the first range with a second range of storage.

RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 16/001,827, filed Jun. 6, 2018, which is a continuation of U.S.patent application Ser. No. 15/667,529, filed Aug. 2, 2017, issued asU.S. Pat. No. 10,019,201 on Jul. 10, 2018, which is a continuation ofU.S. patent application Ser. No. 15/419,886, filed Jan. 30, 2017, issuedas U.S. Pat. No. 9,747,039 on Aug. 29, 2017, which claims the benefit ofU.S. Provisional Patent Application No. 62/404,109, filed Oct. 4, 2016,all of which are incorporated by reference herein.

BACKGROUND

Storage systems, such as enterprise storage systems, may include acentralized or de-centralized repository for data that provides commondata management, data protection, and data sharing functions, forexample, through connections to computer systems.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated by way of example, and not by wayof limitation, and can be more fully understood with reference to thefollowing detailed description when considered in connection with thefigures as described below.

FIG. 1 illustrates an example system for data storage, in accordancewith some implementations.

FIG. 2 illustrates an example system for data storage, in accordancewith implementations.

FIG. 3 illustrates an example system for managing reservations overmultiple paths, in accordance with some implementations.

FIG. 4 is a flow diagram illustrating a method for managing reservationsover multiple paths, in accordance with some implementations.

FIG. 5 is a flow diagram illustrating method of granting a reservationfor the access to the storage drive, in accordance with someimplementations.

FIG. 6 illustrates an example system for managing reservations usingvirtualization techniques, in accordance with some implementations.

FIG. 7 illustrates an example system for managing reservations usinghigh availability storage controllers, in accordance with someimplementations.

FIG. 8 illustrates an example system for managing reservations usingsubmission queues, in accordance with some implementations.

FIG. 9 depicts an example computer system 900 which can perform any oneor more of the methods described herein.

DETAILED DESCRIPTION

In some systems, such as enterprise storage systems using multiple hostcontrollers, a reservations system may be implemented to control accessto shared devices, such as storage drives. An initiator (e.g., hostcontroller) may set a reservation on a logic unit of a storage drive toprevent another initiator (e.g., a different host controller) frommaking changes to the logical unit. In implementations, a logical unitof storage may logically identify a quantity of storage, such as aquantity of non-volatile (NV) memory of a storage drive. Some storagesystems may implement multiple stages of communications to handlereservations. For example, a host controller of a storage array may senda reservation to a storage controller (e.g., a first stage) of adifferent storage array over Ethernet. The storage controller maycommunicate the reservation in a different protocol than the first stageto a drive controller (e.g., second stage) of the storage drive.Systems, such as storage systems, having multiple stages over which areservation is passed presents challenges. In some instances, areservation may not be passed directly through the first stage to thesecond stage because the protocol of the first stage may not becompatible with the second stage. In some instances, reservationmanagement may be handled by one or more of the different stages, e.g.,stage 1 storage controllers or stage 2 drive controllers. Coordinatedcommunication between different stages and within the same stagepresents additional challenges, in particular when multiplecommunication paths and multiple controllers are used within a stage.Great care must be taken to ensure that multiple host controllers do nothave the same access to a storage drive at the same time, which mayresult in data corruption.

Aspects of the present disclosure address the above-mentioned and otherdeficiencies by modifying a reservation at a first stage and tying themodifying reservation for one logical unit to another logical unit atthe storage drive.

In some implementations, a storage controller may receive, from thefirst host controller, a reservation command to acquire access to astorage drive that is shared by a second host controller of themulti-host storage system. The reservation command includes a first hostidentifier to identify the first host controller. The storage controllermay modify the first reservation command by replacing the first hostidentifier with a first logical unit identifier that is associated withthe first host controller and that identifies a first logical unit ofstorage of the storage drive. The storage controller may send, to thedrive controller, the modified first reservation command including thefirst logical unit identifier to a drive controller of the storagedrive. The drive controller may grant a reservation for the access tothe storage drive on behalf of the first host controller based on thefirst logical unit identifier.

It may be noted that aspects of the present disclosure address theabove-mentioned and other deficiencies using different implementationsas described herein.

FIG. 1 illustrates an example system for data storage, in accordancewith some implementations. System 100 (also referred to as “storagesystem” herein) includes numerous elements for purposes of illustrationrather than limitation. It may be noted that system 100 may include thesame, more, or fewer elements configured in the same or different mannerin other implementations.

System 100 includes a number of computing devices 164. Computing devices(also referred to as “client devices” herein) may be for example, aserver in a data center, a workstation, a personal computer, a notebook,or the like. Computing devices 164 are coupled for data communicationsto one or more storage arrays 102 through a network 158, such as astorage area network (SAN), or a local area network (LAN) 160.

The network 158 may be implemented as any number of physical networks,such as a LAN or SAN. The network 158 may be implemented with a varietyof data communications fabrics, devices, and protocols. For example, thefabrics for network 158 may include Fibre Channel, Ethernet, Infiniband,Serial Attached Small Computer System Interface (SAS), or the like. Datacommunications protocols for use with network 158 may include AdvancedTechnology Attachment (ATA), Fibre Channel Protocol, Small ComputerSystem Interface (SCSI), Internet Small Computer System Interface(iSCSI), HyperSCSI, Non-Volatile Memory Express (NVMe) over Fabrics, orthe like. It may be noted that network 158 is provided for illustration,rather than limitation. Other data communication couplings may beimplemented between computing devices 164 and storage arrays 102.

The LAN 160 may also be implemented with a variety of fabrics, devices,and protocols. For example, the fabrics for LAN 160 may include Ethernet(802.3), wireless (802.11), or the like. Data communication protocolsfor use in LAN 160 may include Transmission Control Protocol (TCP), UserDatagram Protocol (UDP), Internet Protocol (IP), HyperText TransferProtocol (HTTP), Wireless Access Protocol (WAP), Handheld DeviceTransport Protocol (HDTP), Session Initiation Protocol (SIP), Real TimeProtocol (RTP), or the like.

Storage arrays 102 may provide persistent data storage for the computingdevices 164. Storage array 102A may be contained in a chassis (notshown), and storage array 102B may be contained in another chassis (notshown), in implementations. Storage array 102A and 102B may include oneor more storage array controllers 110 (also referred to as “controller”herein). A storage array controller 110 may be embodied as a module ofautomated computing machinery comprising computer hardware, computersoftware, or a combination of computer hardware and software. In someimplementations, the storage array controllers 110 may be configured tocarry out various storage tasks. Storage tasks may include writing datareceived from the computing devices 164 to storage array 102, erasingdata from storage array 102, retrieving data from storage array 102 andproviding data to computing devices 164, monitoring and reporting ofdisk utilization and performance, performing redundancy operations, suchas Redundant Array of Independent Drives (RAID) or RAID-like dataredundancy operations, compressing data, encrypting data, and so forth.

Storage array controller 110 and drive controllers (described withrespect to FIG. 3 ) may be implemented in a variety of ways, includingas a Field Programmable Gate Array (FPGA), a Programmable Logic Chip(PLC), an Application Specific Integrated Circuit (ASIC), System-on-Chip(SOC), or any computing device that includes discrete components such asa processing device, central processing unit, computer memory, orvarious adapters. Storage array controller 110 may include, for example,a data communications adapter configured to support communications viathe network 158 or LAN 160. In some implementations, storage arraycontroller 110 may be independently coupled to the LAN 160. Inimplementations, storage array controller 110 may include an I/Ocontroller or the like that couples the storage array controller 110 fordata communications, through a midplane (not shown), to a persistentstorage resource 170 (also referred to as a “storage resource” or“shelf” herein). The persistent storage resource 170 main include anynumber of storage drives 171 (also referred to as “storage devices” or“storage modules” herein) and any number of non-volatile Random AccessMemory (NVRAM) devices (not shown).

In some implementations, the NVRAM devices of a persistent storageresource 170 may be configured to receive, from the storage arraycontroller 110, data to be stored in the storage drives 171. In someexamples, the data may originate from computing devices 164. In someexamples, writing data to the NVRAM device may be carried out morequickly than directly writing data to the storage drive 171. Inimplementations, the storage array controller 110 may be configured toutilize the NVRAM devices as a quickly accessible buffer for datadestined to be written (e.g., flushed) to the storage drives 171.Latency for write requests using NVRAM devices as a buffer may beimproved relative to a system in which a storage array controller 110writes data directly to the storage drives 171. In some implementations,the NVRAM devices may be implemented with computer memory in the form ofhigh bandwidth, low latency RAM. The NVRAM device is referred to as“non-volatile” because the NVRAM device may receive or include a uniquepower source that maintains the state of the RAM after main power lossto the NVRAM device. Such a power source may be a battery, one or morecapacitors, or the like. In response to a power loss, the NVRAM devicemay be configured to write the contents of the RAM to a persistentstorage, such as the storage drives 171.

In implementations, storage drive 171 may refer to any device configuredto record data persistently, where “persistently” or “persistent” refersas to a device's ability to maintain recorded data after loss of power.In some implementations, storage drive 171 may correspond to non-diskstorage media. For example, the storage drive 171 may be one or moresolid-state drives (SSDs), flash memory based storage, any type ofsolid-state non-volatile memory, or any other type of non-mechanicalstorage device. In other implementations, storage drive 171 may includemay include mechanical or spinning hard disk, such as hard-disk drives(HDD). In implementations, a storage drive 171 may contain one or morephysical packages (e.g., packages with pins to connect to a circuitboard) where each physical package contains one or more non-volatilememory die.

In some implementations, the storage array controllers 110 may beconfigured for offloading device management responsibilities fromstorage drive 171 in storage array 102. For example, storage arraycontrollers 110 may manage control information that may describe thestate of one or more memory blocks in the storage drives 171. Thecontrol information may indicate, for example, that a particular memoryblock has failed and should no longer be written to, that a particularmemory block contains boot code for a storage array controller 110, thenumber of program-erase (P/E) cycles that have been performed on aparticular memory block, the age of data stored in a particular memoryblock, the type of data that is stored in a particular memory block, andso forth. In some implementations, the control information may be storedwith an associated memory block as metadata. In other implementations,the control information for the storage drives 171 may be stored in oneor more particular memory blocks of the storage drives 171 that areselected by the storage array controller 110. The selected memory blocksmay be tagged with an identifier indicating that the selected memoryblock contains control information. The identifier may be utilized bythe storage array controllers 110 in conjunction with storage drives 171to quickly identify the memory blocks that contain control information.For example, the storage controllers 110 may issue a command to locatememory blocks that contain control information. It may be noted thatcontrol information may be so large that parts of the controlinformation may be stored in multiple locations, that the controlinformation may be stored in multiple locations for purposes ofredundancy, for example, or that the control information may otherwisebe distributed across multiple memory blocks in the storage drive 171.

In implementations, storage array controllers 110 may offload devicemanagement responsibilities from storage drives 171 of storage array 102by retrieving, from the storage drives 171, control informationdescribing the state of one or more memory blocks in the storage drives171. Retrieving the control information from the storage drives 171 maybe carried out, for example, by the storage array controller 110querying the storage drives 171 for the location of control informationfor a particular storage drive 171. The storage drives 171 may beconfigured to execute instructions that enable the storage drive 171 toidentify the location of the control information. The instructions maybe executed by a controller (not shown) associated with or otherwiselocated on the storage drive 171 and may cause the storage drive 171 toscan a portion of each memory block to identify the memory blocks thatstore control information for the storage drives 171. The storage drives171 may respond by sending a response message to the storage arraycontroller 110 that includes the location of control information for thestorage drive 171. Responsive to receiving the response message, storagearray controllers 110 may issue a request to read data stored at theaddress associated with the location of control information for thestorage drives 171.

In other implementations, the storage array controllers 110 may furtheroffload device management responsibilities from storage drives 171 byperforming, in response to receiving the control information, a storagedrive management operation. A storage drive management operation mayinclude, for example, an operation that is typically performed by thestorage drive 171 (e.g., the controller (not shown) associated with aparticular storage drive 171). A storage drive management operation mayinclude, for example, ensuring that data is not written to failed memoryblocks within the storage drive 171, ensuring that data is written tomemory blocks within the storage drive 171 in such a way that adequatewear leveling is achieved, and so forth.

It may be noted that in other implementations, some device managementresponsibilities may be moved to storage drive 171. For example, storagedrive 171 may handle the arbitration of reservation commands andinput-output (I/O) commands sent by controller 110. In someimplementations, I/O commands may include a write command, a readcommand, or a flush command (e.g., move data stored on NVRAM to storagedrive 171). Other I/O commands may be implemented. Additional details ofreservation arbitration are further described at least with respect toFIG. 2 .

In implementations, storage array 102 may implement two or more storagearray controllers 110. In some implementations, storage array 102 mayimplement multiple host controllers in a multi-host storage system. Forexample, storage array 102A may include storage array controllers 110Aand storage array controllers 110B (also referred to as “host controller110A” and “host controller 110B” respectively, herein). At a giveninstance, a single storage array controller 110 (e.g., storage arraycontroller 110A) of a storage system 100 may be designated with primarystatus (also referred to as “primary controller” or “primary hostcontroller” herein), and other storage array controllers 110 (e.g.,storage array controller 110A) may be designated with secondary status(also referred to as “secondary controller” or “secondary hostcontroller” herein). The status of storage array controllers 110 maychange during run-time. For example, storage array controller 110A maybe designated with secondary status, and storage array controller 110Bmay be designated with primary status.

In implementations, the primary controller may have a particular access(e.g., access rights) to persistent storage resource 170, such aspermission to alter data (e.g., write) in persistent storage resource170 while excluding the same access to the secondary controller. In someimplementation, the access rights may include write access, read access,erase access, or read-write access. It may be noted that differentaccess rights may also be implemented, such as write exclusive access,exclusive access, write exclusive access-registrants only, exclusiveaccess-registrants only, write exclusive access-all registrants,exclusive access-all registrants, for example. In implementations, atleast some of the access rights of the primary controller may supersedethe rights of the secondary controller. For instance, the secondarycontroller may not have permission to write data in persistent storageresource 170 when the primary controller has the write access.

In some implementations, a primary controller, such as storage arraycontroller 110A, may serve as the primary controller for one or morestorage arrays 102, and a second controller, such as storage arraycontroller 110B, may serve as the secondary controller for the one ormore storage arrays 102. For example, storage array controller 110A maybe the primary controller for storage array 102A and storage array 102B,and storage array controller 110B may be the secondary controller forstorage array 102A and 102B. In some implementations, a primarycontroller, such as storage array controller 110A, may serve as theprimary controller for one or more storage drives 171 of storage arrays102, and a second controller, such as storage array controller 110B, mayserve as the primary controller for one or more storage drives 171 ofstorage arrays 102 for which storage array controller 110A does not haveprimary status. It may be noted that in implementations, either storagearray controller 110A or storage array controller 110B may be theprimary controller for a particular storage drive 171, but not both.Both storage array controller 110A and storage array controller 110Bhaving primary status with respect to a particular storage drive 171 orstorage array may result in corruption of data, for example.

In some implementations, storage array controllers 110C and 110D (alsoreferred to as “storage processor modules” or “storage controller”herein) may neither have primary or secondary status. Storage arraycontrollers 110C and 110D, implemented as storage processor modules, mayact as a communication interface between the primary and secondarycontrollers (e.g., storage array controllers 110A and 110B,respectively) and storage array 102B. For example, storage arraycontroller 110A of storage array 102A may send a write request, vianetwork 158, to storage array 102B. The write request may be received byboth storage array controllers 110C and 110D of storage array 102B(e.g., multi-path). Storage array controllers 110C and 110D mayfacilitate the communication, e.g., send the write request to theappropriate storage drive 171. It may be noted that in someimplementations storage processor modules may be used to increase thenumber of storage drives controlled by the primary and secondarycontrollers.

In implementations, storage array controllers 110 are communicativelycoupled, via a midplane (not shown), to one or more storage drives 171and to one or more NVRAM devices (not shown) that are included as partof a storage array 102. The storage array controllers 110 may be coupledto the midplane via one or more data communications links and themidplane may be coupled to the storage drives 171 and the NVRAM devicesvia one or more data communications links. The data communications linksdescribed above are collectively illustrated by data communicationslinks 108 and may include a Peripheral Component Interconnect Express(PCIe) bus, for example.

In some implementations, system 100 may be designed with principles ofhigh availability (HA) architecture. High availability may refer tosystems that are durable and designed to operate continuously byaccommodating for failure using redundant components. For example, amulti-host storage system using controller 110A and 110B may accommodatethe failure of one controller (e.g., controller 110A or controller 110B)and continuously perform the designated operations for system 100.Similarly, implementing multiple storage processor modules, such asstorage array controller 110C and storage array controller 110B, mayaccommodate the failure of one of the storage processor modules.

It may be noted that readers will appreciate that the storage systems,such as system 100, and the components that are contained in suchstorage systems, as described in the present disclosure, are includedfor explanatory purposes and do not represent limitations as to thetypes of systems that may accumulate application-level statistics. Infact, storage systems configured for accumulating application-levelstatistics may be embodied in many other ways and may include fewer,additional, or different components. For example, storage within storagesystems configured for accumulating application-level statistics may beembodied as block storage where data is stored in blocks, and each blockessentially acts as an individual hard drive. Alternatively, storagewithin storage systems configured for accumulating application-levelstatistics may be embodied as object storage, where data is managed asobjects. Each object may include the data itself, a variable amount ofmetadata, and a globally unique identifier, where object storage can beimplemented at multiple levels (e.g., device level, system level,interface level). In addition, storage within storage systems configuredfor accumulating application-level statistics may be embodied as filestorage in which data is stored in a hierarchical structure. Such datamay be saved in files and folders, and presented to both the systemstoring it and the system retrieving it in the same format. Such datamay be accessed using the Network File System (‘NFS’) protocol for Unixor Linux, Server Message Block (‘SMB’) protocol for Microsoft Windows,or in some other manner.

FIG. 2 illustrates an example system for data storage, in accordancewith some implementations. Storage array controller 210 illustrated inFIG. 2 may similar to the storage array controllers 110 described withrespect to FIG. 1 or drive controllers 373 described with respect toFIG. 3 . In one example, storage array controller 210 may be similar tostorage array controller 110A or storage array controller 110B. Storagearray controller 210 includes numerous elements for purposes ofillustration rather than limitation. It may be noted that storage arraycontroller 210 may include the same, more, or fewer elements configuredin the same or different manner in other implementations. It may benoted that elements of FIG. 1 may be included below to help illustratefeatures of storage array controller 210.

Storage array controller 210 may include one or more processing devices232 and random access memory (RAM) 236. Processing device 232 (orcontroller 210) represents one or more general-purpose processingdevices such as a microprocessor, central processing unit, or the like.More particularly, the processing device 232 may be a complexinstruction set computing (CISC) microprocessor, reduced instruction setcomputing (RISC) microprocessor, very long instruction word (VLIW)microprocessor, or a processor implementing other instruction sets orprocessors implementing a combination of instruction sets. Theprocessing device 232 may also be one or more special-purpose processingdevices such as an application specific integrated circuit (ASIC), afield programmable gate array (FPGA), a digital signal processor (DSP),network processor, or the like.

The processing device 232 may be connected to the RAM 236 via a datacommunications link 230, which may be embodied as a high speed memorybus such as a Double-Data Rate 4 (DDR4) bus. Stored in RAM 236 is anoperating system 246. In some implementations, reservation application248 is stored in RAM 236. Reservation application 248 may includecomputer program instructions for managing and arbitrating reservationsfor access to storage drives. In implementations, the storage arraycontroller 210 may execute the reservation application 248 to perform amethod of receiving, from a first host controller in a multi-hoststorage system and by a storage controller, a first reservation commandto acquire access to a storage drive that is shared by a second hostcontroller of the multi-host storage system, the reservation commandincluding a first host identifier to identify the first host controller.The method also includes modifying, by the storage controller, the firstreservation command by translating the first host identifier into afirst logical unit identifier that is associated with the first hostcontroller and that identifies a first logical unit of storage of thestorage drive. The method also includes sending the modified firstreservation command comprising the first logical unit identifier to adrive controller of the storage drive. The method responsive toreceiving the modified first reservation command, granting, by the drivecontroller of the storage drive, a reservation for the access to thestorage drive of the first logical unit of storage on behalf of thefirst host controller based on the first logical unit identifier. Inimplementations, reservation application 248, may include multiplecomponents, such reserver 340, reservation proxy 342, and reservationarbiter. In implementations, the multiple components of reservationapplication 248 may execute different features of reservationapplication 248. In implementations, the components of reservationapplication may reside on or be performed by different devices orelements of a storage system, as illustrated with respect to FIG. 3 .

It may be noted that the reservation application 248 and the operatingsystem 246 shown in RAM 236 for purposes of illustration, rather thanlimitation. Many components of reservation application 248 or theoperating system 246 may also be stored in non-volatile memory such as,for example, persistent storage resource 170 described with respect toFIG. 1 .

In implementations, storage array controller 210 includes one or morehost bus adapters 218 that are coupled to the processing device 232 viaa data communications link 224. In implementations, host bus adapters218 may be computer hardware that connects a host system (e.g., thestorage array controller) to other network and storage arrays. In someexamples, host bus adapters 218 may be a Fibre Channel adapter thatenables the storage array controller 210 to connect to a SAN, anEthernet adapter that enables the storage array controller 210 toconnect to a LAN, or the like. Host bus adapters 218 may be coupled tothe processing device 232 via a data communications link 224 such as,for example, a PCIe bus.

In implementations, storage array controller 210 may include a host busadapter 240 that is coupled to an expander 242. The expander 242 may beused to attach a host system to a larger number of storage drives. Theexpander 242 may, for example, be a SAS expander utilized to enable thehost bus adapter 240 to attach to storage drives in an implementationwhere the host bus adapter 240 is embodied as a SAS controller.

In implementations, storage array controller 210 may include a switch244 coupled to the processing device 232 via a data communications link238. The switch 244 may be a computer hardware device that can createmultiple endpoints out of a single endpoint, thereby enabling multipledevices to share a single endpoint. The switch 244 may, for example, bea PCIe switch that is coupled to a PCIe bus (e.g., data communicationslink 238) and presents multiple PCIe connection points to the midplane.

In implementations, storage array controller 210 includes a datacommunications link 234 for coupling the storage array controller 210 toother storage array controllers. In some examples, data communicationslink 234 may be a QuickPath Interconnect (QPI) interconnect.

FIG. 3 illustrates an example system for managing reservations overmultiple paths, in accordance with some implementations. Inimplementations, system 300 illustrated in FIG. 3 may be similar to andinclude similar elements as system 100 described with respect to FIG. 1. Some elements of system 100 have been included for purposes ofillustration, rather than limitation. Other elements of system 100 havenot been included so as not to obscure the implementation, rather thanfor limitation. It may be noted that system 300 may include the same,more, or fewer elements configured in the same or different manner inother implementations. For purposes of illustration, rather thanlimitation, in system 300 storage array controller 110A is the primarycontroller (e.g., primary host controller), storage array controller110B is the secondary controller (e.g., secondary host controller in themulti-host storage system), and storage array controller 110C and 110Dare storage processor modules (e.g., storage controller). It may benoted that in other implementations, storage array controllers 110 mayhave different statuses or functions. For purposes of illustration,rather than limitation, in system 300 persistent storage resource 170Bis shown with a single storage drive 171D. In implementations,persistent storage resource 170B may include multiple storage drives 171with similar features as described with respect to storage drive 171D.It may also be noted the operations described with respect to storagedrive 171D, may be performed in a similar manner for and by additionalstorage drives.

In some implementations, a storage drive, such as storage drive 171D,includes one or more ports 372 (e.g., multiport storage drive). A port372 may be coupled to a respective storage array controller 110. Forexample, port 372A is coupled to storage array controller 110C via datacommunications link 108C. Port 372B is coupled to storage arraycontroller 110D via data communications link 108D. A port 372 may beassociated with a particular drive controller 373. For example, port372A is associated drive controller 373A. Port 372B is associated withdrive controller 373B. Ports 372 may transmit data to and from theassociated drive controllers 373. In implementations, communicationsbetween storage array controllers 110C and 100D and the respectivedriver controller 373 may be compatible with a non-fabric-basedstandard, such as the NVMe standard.

Drive controller 373A may have access to both logical unit of storage352A and logical unit of storage 352B. Similarly, drive controller 373Bmay have access to both logical unit of storage 352A and logical unit ofstorage 352B. In implementations, a specific logical unit identifieridentifies a particular logical unit of storage drive 171D. A logicalunit identifier may be a value used to identify a specific logical unitof storage of storage drive 171. The logical unit of storage maylogically identify a quantity of storage, such as a quantity ofnon-volatile (NV) memory 356 of storage drive 171D. In someimplementations, the logical unit identifier is a namespace identifierand the logical unit is a namespace compatible with the NVMe standard.

In implementations, a total usable storage capacity of the NV memory 356may be divided by the system 300 into one or more namespaces. Forexample, the usable storage capacity of K NV memory 356 may be dividedinto M namespaces, wherein K and M are positive integers but notnecessarily equal in value. As shown in FIG. 3 , M namespaces includelogical unit of storage 352A (also referred to as “namespace 1”) andlogical unit of storage 352B (also referred to as “namespace 2”). Eachnamespace may represent a slice of storage capacity provided by the NVmemory 356. It may be noted that each namespace may have an equal orunequal storage capacity. In implementations, namespace 1 and namespace2 may refer to the same slice of storage capacity provided by the NVmemory 356. In implementations, namespace 1 and namespace 2 may eachrefer to the total usable storage capacity of the NV memory 356.

In implementations, storage array controller 110A and 110B may be hostcontrollers in a multi-host system, such as system 300. Storage arraycontrollers 110A and 100B may send reservations for access to storagedrive 171D. It may be noted that storage array controllers may sendreservations for access to each of the multiple storage drives (notshown). In one implementation, storage array controller 110A and 110Bmay include reserver 340A and 340B, respectively. Reserver 340A and 340Bmay perform reservation operations on behalf of storage array controller110A and 110B, respectively, as described herein.

In implementations, storage array controller 110A and 110B sendreservations 334 and 336, respectively, to another storage array, suchas storage array 102B. Reservations 334 and 336 may also be referred toas a “reservation command” herein. Reservations 334 and 336 may berequests or commands that allow two or more host controllers (e.g.,storage array controller 110A and 110B) to coordinate access (e.g., readaccess, write access, erase access, etc.) to a storage drive, such asstorage drive 171D. In implementations, reservations 334 and 336 mayinclude commands such as reservation acquire, reservation register,reservation release, reservation report, among others. Reservations 334and 336 may refer to a reservation acquire command herein, unlessotherwise described.

In implementations, reservations 334A and 334B may include a hostidentifier that identifies storage array controller 110A. For example, ahost identifier may be an N-bit identifier that uniquely identifies astorage array controller, such as storage array controller 110A.

In implementations, the reservations 334 and 336 may be sent viamultipath. Multipath may refer to two or more physical paths between afirst device (e.g., storage array controller 110A) and a target device(e.g., storage drive 171D). Multipath may improve fault-tolerance andperformance, or may be part of an HA architecture. For example,reservations 334A and 334B may be sent by storage array controller 110Ato storage array controller 110C and 110D, respectively. Similarly,reservations 336A and 336B may be sent by storage array controller 110Bto storage array controller 110C and 110D, respectively. Inimplementations, reservations 334A and 334B may include the samecontent, but be sent to different devices, such as storage arraycontroller 110C and 110D, respectively. Similarly, reservations 336A and336B may include the same content, but be sent to different devices,such as storage array controller 110C and 110D, respectively.

In implementations, signal path 330A represents the signal path ofreservation 334A. In signal path 330A, reservation 334A is sent bystorage array controller 110A to storage array controller 110C.Similarly, in signal path 330B, reservation 334B is sent by storagearray controller 110A to storage array controller 110D. In signal path332A, reservation 336A is sent by storage array controller 110B tostorage array controller 110C. In signal path reservation 336B is sentby storage array controller 110B to storage array controller 110D.

It may also be noted that in implementations the reservations 334 and336 travel multiple stages. For example, reservation 334A is sent bystorage array controller 110A to storage array controller 110C (stage1). Storage array controller 110C may send a modified reservation todrive controller 373A (stage 2). In implementations, the protocolsbetween of stages may be different from one another. For example, instage 1 the storage array controller 110A may communicate to storagearray controller 110C over a fabric-based network using a fabric-basedprotocol. Reservations 334 or 336 may be sent over a network, such asnetwork 158 of FIG. 1 . The network may be fabric-based network usingdata formats compatible with a particular fabric standard, such as NVMeover Fabrics. In stage 2, storage array controller 110C may communicateto drive controller 373A using a non-fabric protocol. For example,storage array controller 110C may receive reservation 334A, modifyreservation 334A, and send the modified reservation 334A to storagedrive 171 via data communications link 108C using a non-fabric protocol,such as NVMe. In implementations, storage array controller 110A and 110Band drive controllers 373 may not have direct knowledge of one another,and may use storage array controller 110C and 110D to associatecommunications from storage array controller 110A and 110B to drivecontrollers 373, and vice-versa.

In implementations, after a reservation is received by storage arraycontroller 110C and 110D, reservation proxy 342 may translate or modifythe received reservation. For the sake of illustration, rather thanlimitation, the flow of reservation 334A through system 300 will bedescribed. It may be noted that other elements receiving reservationsother than reservation 334A may perform similar operations. Inimplementations, reservation 334A includes a host identifier thatidentifies the sending host controller, such as storage array controller110A. Reservation proxy 342A of storage array controller 110C may modifyreservation 334A by changing the host identifier to a logical unitidentifier that is associated with a particular storage arraycontroller, such as storage array controller 110A.

For example, storage array controller 110C may modify reservation 334Ahaving a host identifier identifying storage array controller 110A witha logical unit identifier identifying logical unit of storage 352A.Similarly, storage array controller 110C may modify reservation 336Ahaving a host identifier identifying storage array controller 110B witha logical unit identifier identifying logical unit of storage 352B.Storage array controller 110C may use a table, common logic, orotherwise, to reference the received host identifier with the associatedlogical unit identifier.

In implementations, storage array controller 110C may also translatereservation 334A from a first protocol (e.g., fabric-based protocol) toanother protocol (e.g., non-fabric protocol). In implementations, amodified reservation may refer to a reservation where at least the hostidentifier has been replaced with the associated logical unitidentifier. In other implementations, a modified reservation may referto a reservation where the host identifier has been replaced with theassociated logical unit identifier and the reservation has beentranslated consistent with another communication standard.

In implementations, the storage array controller 110C sends the modifiedreservation 334A to storage drive 171D via port 372A. The modifiedreservation 334A includes a logical unit identifier that identifieslogical unit of storage 325A. The modified reservation 334A is passed todrive controller 373A. Reservation arbiter 344A of drive controller373A, responsive to receiving the modified reservation 334A, checkscurrent reservations for access to logical unit of storage 352A. If noother reservations are held for logical unit of storage 352A and noother reservations are associated with logical unit of storage 352A,reservation arbiter 344 may grant and hold the reservation for logicalunit of storage 352A based on the modified reservation 334A. Inimplementations, reservation arbiter 344 may associate or tie thereservation for logical unit of storage 352A to another logical unit ofstorage, such as logical unit of storage 352B. It may be noted thatwithout tying the logical unit of storage 352B to the reservation forthe logical unit of storage 352A, in some implementations a hostcontroller may still be able to access logical unit of storage 352B. Areservation held for logical unit of storage 352A and associated withlogical unit of storage 352A, allows storage drive 171D to grant accessto both logical unit of storage 352A and 352B in response to an I/Ocommand that includes logical unit identifier for logical unit ofstorage 352A, and deny access to both logical unit of storage 352A and352B in response to an I/O command that includes a logical unitidentifier of logical unit of storage 352B. A reservation held forlogical unit of storage 352A and associated with logical unit of storage352A, is a reservation to the storage drive on behalf of the storagearray controller 110A, rather than storage array controller 110B. It maybe noted that reservations and I/O commands including logical unitidentifiers of logical units of storage that are associated with or tiedto a reservation held by another logical unit of storage may be denied.In implementations where logical unit of storage 352A and logical unitof storage 352B each represent the same total usable storage capacity ofthe NV memory 356, a reservation held for logical unit of storage 352Aand associated with logical unit of storage 352A, is a reservation tothe entire storage drive on behalf of the storage array controller 110A,rather than storage array controller 110B.

It may also be noted that drive controller 373A and drive controller373B may communicate directly or through another component, such acommon logic block (not shown), to coordinate the arbitration ofreservations and I/O commands. For example, to determine if areservation has been granted for logical unit of storage 352A andassociated with logical unit of storage 352A, drive controllers 373(responsive to receiving subsequent reservations or I/O commands) mayaccess a common logic block that keeps track of the current reservation(e.g., master reservation holder). It may also be noted that two logicalunits are shown for purposes of illustration rather than limitation. Inother implementations, additional logical units of storage 352 may beused, for example in implementations that use three or more drivecontrollers 373.

In implementations, where storage drive 171D holds a reservation onbehalf of storage array controller 110A (e.g., a reservation for logicalunit of storage 352A that is tied to logical unit of storage 352B andwithout direct knowledge the reservation is on behalf of storage arraycontroller 110A), storage drive 171D may receive additional reservationcommands from storage array controller 110B (via storage arraycontroller 110C or 110D). In one implementation, storage arraycontroller 110C may receive from storage array controller 110Breservation 336A. Reservation 336A may be a reservation command toacquire access (e.g., the same access as storage array controller 110Ahas been granted) to storage drive 171D. Reservation 336A may include adifferent host identifier that identifies storage array controller 110B.Storage array controller 110C may determine the association between thehost identifier in the reservation 336A and the appropriate logical unitidentifier. Storage array controller 110C may modify reservation 336A toreplace the host identifier identifying storage array controller 110Bwith a logical unit identifier that identifies logical unit of storage352B. Storage array controller 110 may send the modified reservation336A to drive controller 373A via port 372A. After receiving themodified reservation 336A, drive controller 373A may identify logicalunit of storage 352B using the logical unit identifier in modifiedreservation 336A. Storage array controller 110A may determine that areservation is being held for logical unit of storage 352A and thereservation is associated with logical unit of storage 352B, and denythe reservation for logical unit of storage 352B.

In implementations, where storage drive 171D holds a reservation onbehalf of storage array controller 110A (e.g., a reservation for logicalunit of storage 352A that is tied to logical unit of storage 352B),storage drive 171D may receive I/O commands from storage arraycontroller 110B. In one implementation, storage array controller 110Cmay receive from storage array controller 110B an I/O command (e.g.,write command). The I/O command may include a host identifier thatidentifies storage array controller 110B. Storage array controller 110Amay determine the association between the host identifier in the I/Ocommand and the appropriate logical unit identifier. Storage arraycontroller 110C may modify the I/O command to replace the hostidentifier identifying storage array controller 110B with a logical unitidentifier that identifies logical unit of storage 352B. Storage arraycontroller 110C may send the modified I/O command to drive controller373A via port 372A. After receiving the I/O command, drive controller373A may identify logical unit of storage 352B using the logical unitidentifier in I/O command. Storage array controller 110A may determinethat a reservation is being held for logical unit of storage 352A andthe reservation is associated with logical unit of storage 352B, anddeny the execution of the I/O action (e.g., read, write, etc.) based onthe modified I/O command.

In implementations, where storage drive 171D holds a reservation onbehalf of storage array controller 110A (e.g., a reservation for logicalunit of storage 352A that is tied to logical unit of storage 352B),storage drive 171D may receive I/O commands from storage arraycontroller 110A. In one implementation, storage array controller 110Cmay receive from storage array controller 110A, an I/O command (e.g.,write command). The I/O command may include a host identifier thatidentifies storage array controller 110A. Storage array controller 110Amay determine the association between the host identifier in the I/Ocommand and the appropriate logical unit identifier. Storage arraycontroller 110C may modify the I/O command to replace the hostidentifier identifying storage array controller 110A with a logical unitidentifier that identifies logical unit of storage 352A. Storage arraycontroller 110C may send the modified I/O command to drive controller373A via port 372A. After receiving the I/O command, drive controller373A may identify logical unit of storage 352A using the logical unitidentifier in I/O command. Storage array controller 110A may determinethat the reservation is being held for logical unit of storage 352A andthat the reservation is associated with logical unit of storage 352B,and matches the logical unit of storage identified in the modified I/Ocommand. Drive controller 373A may perform the I/O action specified inthe modified I/O command. It may be noted that communications sent fromdrive controllers 373 to storage array controller 110C and 110D mayinclude logical unit identifiers that correspond to the grantedreservation, and storage array controller 110C and 110D may modify thecommunications by replacing the logical unit identifiers with theappropriate host identifiers before sending the modified communicationsto storage array controller 110A and 110B. In implementations, thefirmware of storage drive 171 may be extended (e.g., reservation arbiter344) to cooperated with a modified reservation 334 or 336 without thecoordination between one or more storage processor modules, such asstorage array controller 110C and 110D.

FIG. 4 is a flow diagram illustrating a method for managing reservationsover multiple paths, in accordance with some implementations. Method 400may be performed by processing logic that includes hardware (e.g.,circuitry, dedicated logic, programmable logic, microcode), software(e.g., instructions run on a processing device to perform hardwaresimulation), or a combination thereof. In one implementation, storagearray controllers 110A-D, and drive controllers 373A-B may perform someor all the operations described herein.

Method 400 begins at block 405 where processing logic receives, from afirst host controller in a multi-host storage system, a firstreservation command to acquire access to a storage drive that is sharedby a second host controller of the multi-host storage system. Thereservation command includes a first host identifier to identify thefirst host controller. At block 410, processing logic modifies the firstreservation command by replacing the first host identifier with a firstlogical unit identifier that is associated with the first hostcontroller and that identifies a first logical unit of storage of thestorage drive. At block 415, processing logic sends the modified firstreservation command including the first logical unit identifier to adrive controller of the storage drive. At block 420, processing logic,responsive to receiving the modified first reservation command, grants areservation for the access to the storage drive on behalf of the firsthost controller based on the first logical unit identifier.

FIG. 5 is a flow diagram illustrating method of granting a reservationfor the access to the storage drive, in accordance with someimplementations. Method 500 may be performed by processing logic thatincludes hardware (e.g., circuitry, dedicated logic, programmable logic,microcode), software (e.g., instructions run on a processing device toperform hardware simulation), or a combination thereof. In oneimplementation, storage array controllers 110A-D, and drive controllers373A-B may perform some or all the operations described herein.

Method 500 begins at block 505 where processing logic holds thereservation for the first logical unit of storage of the storage drivebased on the modified first reservation including the first logical unitidentifier. At block 510, processing logic associates a second logicalunit of storage of the storage drive with the reservation held for thefirst logical unit of storage. At block 515, processing logic grantsaccess to the first logical unit of storage and the second logical unitof storage of the storage drive on behalf of the first host controller,rather than the second host controller, based on the reservation for thefirst logical unit.

FIG. 6 illustrates an example system for managing reservations usingvirtualization techniques, in accordance with some implementations. Insome implementations, the virtualization techniques include techniquesassociated with single root I/O virtualization (SR-IOV) (also referredto as “raw device mapping” (RDM)). In implementations, system 600illustrated in FIG. 6 may be similar to and include similar elements assystem 100 described with respect to FIG. 1 and system 300 describedwith respect to FIG. 3 . Some elements of system 100 and system 300 havebeen included for purposes of illustration, rather than limitation.Other elements of system 100 and system 300 have not been included so asnot to obscure the implementation, rather than for limitation. It may benoted that operations described with respect to system 300, may also beperformed using system 600 even if not explicitly described. It may benoted that system 600 may include the same, more, or fewer elementsconfigured in the same or different manner in other implementations. Forpurposes of illustration, rather than limitation, in system 600 storagearray controller 110A is the primary controller (e.g., primary hostcontroller), storage array controller 110B is the secondary controller(e.g., secondary host controller in the multi-host storage system), andstorage array controller 110C and 110D are storage processor modules(e.g., storage controller). It may be noted that in otherimplementations, storage array controllers 110 may have differentstatuses or functions. For purposes of illustration, rather thanlimitation, in system 600 persistent storage resource 170B is shown witha single storage drive 171D. In implementations, persistent storageresource 170B may include multiple storage drives 171 with similarfeatures as described with respect to storage drive 171D. It may also benoted the operations described with respect to storage drive 171D, maybe performed in a similar manner for and by additional storage drives.

In implementations, SR-IOV may allow each VM or client (e.g., storagearray controller 110C or 110D) to have direct access to hardware, suchas storage drive 171D, in the form of a virtual function (VF). SR-IOVmay allow data, such as storage traffic, to bypass a hypervisor (orvirtual machine manager (VMM))SR-IOV may be supported using internetsmall computer system interface (iSCSI) or fiber channel (FC) protocols,for example.

In implementations, SR-IOV allows a device (e.g., storage drive 171D) toappear to be multiple separate physical devices. A physical function(PF), such as PF 660, may be a peripheral component interconnect express(PCIe) function that supports SR-IOV capabilities. A virtual function,such as VF 662 and VF 664, may be considered a light-weight or low-costPCIe function containing the basic PCIe configuration space andresources necessary for data movement. A virtual function may lackconfiguration resources. The VFs 662 and 664 may be associated with thePF 660 and as such, share the resources of PF 660. The PF 660 maysupervise one or more associated VFs, such as VF 662 and VF 664. Theremay be any suitable number of VFs associated with one PF. Inimplementations, PF 660 and the associated VFs, such as VF 662 and VF664, have access to the same logical unit of storage 352A. Inimplementations, logical unit of storage 352A may be a namespace, suchas namespace 1. In implementations, drive controller 373A iscommunicatively coupled to PF 660 and the associated VFs 662 and 664,and drive controller 373B has is communicatively coupled to the same PF660 and the associated VFs 662 and 664. In some examples, storage arraycontroller 110A and 110B may communicate to storage array controller110C and 110D using a protocol consistent with the NVME over Fabricsstandard. In some implementations, the storage array controller 110A and110B may use networked SCSI, such as iSCSI or SCSI Remote Direct MemoryAccess (RDMA) Protocol (SRP), along with a SCSI to NVMe translation(e.g., NVMe: SCSI translation reference). In some implementations,communication between storage array controllers 110C-110D and drivecontrollers 373 may be consistent with the NVMe standard (e.g., NVMeover PCIe). In other implementations, communication between storagearray controllers 110C-110D and drive controllers 373 may be anotherstorage protocol over PCI, such as a proprietary protocol or SCSI overPCIe (SOP).

In implementations, storage array controller 110A and 110B sendreservations 334 and 336, respectively, to another storage array, suchas storage array 102B. In implementations, reservations 334A and 334Bmay include a host identifier that identifies storage array controller110A.

In implementations, after a reservation is received by storage arraycontroller 110C and 110D, reservation proxy 342 may translate or modifythe received reservation. For the sake of illustration, rather thanlimitation, the flow of reservation 334A through system 300 will bedescribed. It may be noted that other elements receiving reservationsother than reservation 334A may perform similar operations. Inimplementations, reservation 334A includes a host identifier thatidentifies a sending host controller, such as storage array controller110A. Reservation proxy 342A of storage array controller 110C may modifyreservation 334A by changing the host identifier to a virtual functionidentifier that is associated with a particular storage arraycontroller, such as storage array controller 110A. The virtual functionidentifier may identify the particular virtual function (e.g., VF 662 orVF 664) that is associated with a particular host controller.

For example, storage array controller 110C may modify reservation 334Ahaving a host identifier identifying storage array controller 110A witha virtual function identifier identifying logical unit of storage 352A.Similarly, storage array controller 110C may modify reservation 336Ahaving a host identifier identifying storage array controller 110B witha virtual function identifier identifying logical unit of storage 352B.Storage array controller 110C may use a table, common logic, orotherwise, to reference the received host identifier with the associatedvirtual function identifier.

In implementations, storage array controller 110C may also translatereservation 334A from a first protocol (e.g., fabric-based protocol) toanother protocol (e.g., non-fabric protocol). In implementations, amodified reservation may refer to a reservation where at least the hostidentifier has been replaced with the associated virtual functionidentifier. In other implementations, a modified reservation may referto a reservation where the host identifier has been replaced with theassociated virtual function identifier and the reservation has beentranslated consistent with another communication standard.

In implementations, the storage array controller 110C sends the modifiedreservation 334A to storage drive 171D via port 372A. The modifiedreservation 334A includes a virtual function identifier that identifiesvirtual function 662. The modified reservation 334A is passed to drivecontroller 373A. Reservation arbiter 344A of drive controller 373A,responsive to receiving the modified reservation 334A, checks currentreservations for access to virtual function 662. If no otherreservations are held for virtual function 662 and no other reservationsare associated with virtual function 662, reservation arbiter 344 maygrant and hold the reservation for virtual function 662 based on themodified reservation 334A. In implementations, reservation arbiter 344may associate or tie the reservation for virtual function 662 to anothervirtual function, such as virtual function 664. It may be noted thatwithout tying the virtual function 662 to the reservation for thevirtual function 662, in some implementations a host controller maystill be able to access virtual function 664. A reservation held forvirtual function 662 and associated with virtual function 664, allowsstorage drive 171D to grant access to both logical unit of storage 352Ain response to an I/O command that includes a virtual functionsidentifier identifying virtual function 662, and deny access to logicalunit of storage 352A in response to an I/O command that includes avirtual function identifier of virtual function 664. A reservation heldfor virtual function 662 and associated with virtual function 664, is areservation to the storage drive on behalf of the storage arraycontroller 110A, rather than storage array controller 110B. It may benoted that reservations and I/O commands including virtual functionidentifiers of virtual functions that are associated with or tied to areservation held by another virtual function may be denied. Inimplementations where logical unit of storage 352A represents the totalusable storage capacity of the NV memory 356, a reservation held forvirtual function 662 and associated with virtual function 664, is areservation to the entire storage drive 171D on behalf of the storagearray controller 110A, rather than storage array controller 110B.

It may also be noted that drive controller 373A and drive controller373B may communicate directly or through another component, such acommon logic block, to coordinate the arbitration of reservations andI/O commands. For example, to determine if a reservation has beengranted for virtual function 662 and associated with virtual function664, drive controllers 373 (responsive to receiving subsequentreservations or I/O commands) may access a common logic block that keepstrack of the current reservation.

In implementations, where storage drive 171D holds a reservation onbehalf of storage array controller 110A (e.g., a reservation for virtualfunction 662 that is tied to virtual function 664 and without directknowledge the reservation is on behalf of storage array controller110A), storage drive 171D may receive additional reservation commandsfrom storage array controller 110B (via storage array controller 110C or110D). In one implementation, storage array controller 110C may receivefrom storage array controller 110B reservation 336A. Reservation 336Amay be a reservation command to acquire access (e.g., the same access asstorage array controller 110A has been granted) to storage drive 171D.Reservation 336A may include a different host identifier that identifiesstorage array controller 110B. Storage array controller 110C maydetermine the association between the host identifier in the reservation336A and the appropriate virtual function identifier. The associationsbetween host identifiers and virtual function identifiers may be kept ina table or common logic accessible to storage array controller 110C and110D, for example. Storage array controller 110C may modify reservation336A to replace the host identifier identifying storage array controller110B with a virtual function identifier that identifies virtual function664 (that is associated with storage array controller 110B by storagearray controller 110C). Storage array controller 110C may send themodified reservation 336A to drive controller 373A via port 372A. Afterreceiving the modified reservation 336A, drive controller 373A mayidentify virtual function 664 using the virtual function identifier inmodified reservation 336A. Storage array controller 110A may determinethat a reservation is being held for virtual function 662 and thereservation is associated with virtual function 664, and deny thereservation for virtual function 664.

In implementations, where storage drive 171D holds a reservation onbehalf of storage array controller 110A (e.g., a reservation virtualfunction 662 that is tied to virtual function 664), storage drive 171Dmay receive I/O commands from storage array controller 110B. In oneimplementation, storage array controller 110C may receive from storagearray controller 110B an I/O command (e.g., write command). The I/Ocommand may include a host identifier that identifies storage arraycontroller 110B. Storage array controller 110A may determine theassociation between the host identifier in the I/O command and theappropriate virtual function identifier. Storage array controller 110Cmay modify the I/O command to replace the host identifier identifyingstorage array controller 110B with a virtual function identifier thatidentifies logical unit of storage 352B. Storage array controller 110Cmay send the modified I/O command to drive controller 373A via port372A. After receiving the I/O command, drive controller 373A mayidentify virtual function 664 using the logical unit identifier in I/Ocommand. Storage array controller 110A may determine that a reservationis being held for virtual function 662 and the reservation is associatedwith virtual function 664, and deny the execution of the I/O actionbased on the modified I/O command.

In implementations, where storage drive 171D holds a reservation onbehalf of storage array controller 110A (e.g., a reservation for virtualfunction 662 that is tied to virtual function 664), storage drive 171Dmay receive I/O commands from storage array controller 110A. In oneimplementation, storage array controller 110C may receive from storagearray controller 110A, an I/O command (e.g., write command). The I/Ocommand may include a host identifier that identifies storage arraycontroller 110A. Storage array controller 110A may determine theassociation between the host identifier in the I/O command and theappropriate virtual function identifier. Storage array controller 110Cmay modify the I/O command to replace the host identifier identifyingstorage array controller 110A with a virtual function identifier thatidentifies logical unit of storage 352A. Storage array controller 110Cmay send the modified I/O command to drive controller 373A via port372A. After receiving the I/O command, drive controller 373A mayidentify virtual function 662 using the virtual function identifier inI/O command. Storage array controller 110A may determine that thereservation is being held for virtual function 662 and that thereservation is associated with virtual function 664, and matches thevirtual function 662 identified in the modified I/O command. Drivecontroller 373A may perform the I/O action specified in the modified I/Ocommand. It may be noted that communications sent from drive controller373 to storage array controller 110C and 110D may include virtualfunction identifiers that correspond to the granted reservation, andstorage array controller 110C and 110D may modify the communication byreplacing the virtual function identifier with the appropriate hostidentifier before sending the modified communication to storage arraycontroller 110A and 110B.

FIG. 7 illustrates an example system for managing reservations usinghigh availability storage controllers, in accordance with someimplementations. In implementations, system 700 illustrated in FIG. 7may be similar to and include similar elements as system 100 describedwith respect to FIG. 1 , system 300 described with respect to FIG. 3 ,and system 600 described with respect to FIG. 6 . Some elements ofsystem 100, 300, and 600 have been included for purposes ofillustration, rather than limitation. Other elements of system 100, 300,and 600 have not been included so as not to obscure the implementation,rather than for limitation. It may be noted that operations describedwith respect to system 300 and 600, may also be performed using system700 even if not explicitly described. It may be noted that system 700may include the same, more, or fewer elements configured in the same ordifferent manner in other implementations. For purposes of illustration,rather than limitation, in system 700 storage array controller 110A isthe primary controller (e.g., primary host controller), storage arraycontroller 110B is the secondary controller (e.g., secondary hostcontroller in the multi-host storage system), and storage arraycontroller 110C and 110D are storage processor modules (e.g., storagecontroller). It may be noted that in other implementations, storagearray controllers 110 may have different statuses or functions. Forpurposes of illustration, rather than limitation, in system 700persistent storage resource 170B is shown with a single storage drive171D. In implementations, persistent storage resource 170B may includemultiple storage drives 171 with similar features as described withrespect to storage drive 171D. It may also be noted the operationsdescribed with respect to storage drive 171D, may be performed in asimilar manner for and by additional storage drives.

In implementations, reservation arbitration may be handled by storagearray controller 110C and 110D, rather than drive controllers 373. Forexample, storage array controller 110C and 110D receive reservations 334and 336, and rather than translate the host identifier in thereservations, storage array controller 110C and 110D grant and holdreservations, and arbitrate I/O commands. In implementations, storagearray controller 110C and storage array controller 110D coordinatebetween themselves (as shown by the arrow between storage arraycontroller 110C and 110D), to perform reservation and I/O commandarbitration. It may be noted that storage array controller 110C and 110Dmay communicate directly or communicate with common logic (not shown) toperform reservation and I/O command arbitration. Storage arraycontroller 110C and 110D may maintain the reservation until thereservation is complete, and pass the appropriate I/O commands to drivecontrollers 373 when the granted reservation permits. Reservations arehandled by storage array controller 110C and 110D, and not passed tostorage drive 171D. If I/O commands are received from a host controllerother than the host controller holding the reservation, the I/O commandsare not passed (blocked) by storage array controller 110C and 110D tostorage drive 171D.

In implementations, storage array controller 110A and 110B sendreservations 334 and 336, respectively, to another storage array, suchas storage array 102B. Reservations 334 and 336 may be requests orcommands that allow two or more host controllers (e.g., storage arraycontroller 110A and 110B) to coordinate access (e.g., read access, writeaccess, erase access, etc.) to a storage drive, such as storage drive171D. In implementations, reservations 334A and 334B may include a hostidentifier that identifies storage array controller 110A.

In implementations, the reservations 334 and 336 may be sent viamultipath. For example, reservations 334A and 334B may be sent bystorage array controller 110A to storage array controller 110C and 110D,respectively. Similarly, reservations 336A and 336B may be sent bystorage array controller 110B to storage array controller 110C and 110D,respectively. In implementations, reservations 334A and 334B may includethe same content, but be sent to different devices, such as storagearray controller 110C and 110D, respectively. Similarly, reservations336A and 336B may include the same content, but be sent to differentdevices, such as storage array controller 110C and 110D, respectively.

In implementations, after a reservation is received by storage arraycontroller 110C and 110D, reservation arbiter 344 identifies the hostcontroller using the host identifier in the reservation. For the sake ofillustration, rather than limitation, the flow of reservation 334Athrough system 300 will be described. It may be noted that otherelements receiving reservations other than reservation 334A may performsimilar operations. In implementations, reservation 334A includes a hostidentifier that identifies a sending host controller, such as storagearray controller 110A. In implementations, the reservation 334A may besent in a fabric-based protocol.

Reservation arbiter 344A of storage array controller 110C, responsive toreceiving the reservation 334A, checks the current reservation statusfor access to logical unit of storage 352A using the host identifier inreservation 334A. It may be noted that logical unit of storage 352A maybe namespace 1 in an implementation. It may also be noted that storagearray controller 110C and storage array controller 110D may communicatedirectly or through another component, such a common logic block (notshown), to coordinate the arbitration of reservations and I/O commands.For example, to determine if a reservation has been granted for storagearray controller 110A, storage array controller 110C (responsive toreceiving subsequent reservations or I/O commands) may access a commonlogic block that keeps track of the current reservation status.

In implementations, to determine if a reservation is being held, storagearray controller 110C may access a master reservation holder held in acommon logic block. A master reservation holder may hold informationregarding the current reservation status and include information such astype of access and holder of the reservation. The master reservationholder may be common and accessible to both storage array controller110C and 100D, where both storage array controller 110C and 110D areable to read and write to the master reservation holder. In otherimplementations, storage array controller 110C and storage arraycontroller 110D may each hold information regarding the reservationstatus, and communicate to one another in response to a reservation todetermine if both storage array controller 110C and 110D reflect thesame reservation status, determine whether to grant the receivedreservation, and coordinate the information for the reservation statusfor both storage array controllers 110C and 110D. It may be noted thatthe reservation status of each storage drive 171 of storage array 102Bmay be managed by storage array controllers 110C and 110D.

In implementations, responsive to receiving reservation 334A, storagearray controller 110C may check the reservation status. If noreservations are held for storage array controller 110B, reservationarbiter 344 may grant and hold the reservation for storage arraycontroller 110A based on the reservation 334A and associate thereservation with storage array controller 110B. In implementations,reservation arbiter 344 may update the reservation status on the masterreservation holder to indicate that storage array controller 110Acurrently holds the reservation for access. In other implementations,storage array controller 110C may send the reservation 334A (or otherinformation representing a reservation on behalf of storage arraycontroller 110A) to storage array controller 110D. Storage arraycontroller 110D may update the local reservation status associated withstorage array controller 110D, and send a response back to storage arraycontroller 110C. Storage array controller 110C may send a confirmationof the reservation to storage array controller 110A. It may be notedthat if a reservation for access is held for storage array controller110A, a reservation for storage array controller 110B will be denied,and vice versa.

In implementations, responsive to determining the reservation statusesof storage array controller 110C and 110D are not the same, the storagearray controller 110C and 110D may pause processing of I/O commands andupdated the reservation statuses for both storage array controller 110Cand 110D with the received reservation.

In implementations, storage array controller 110C and 110D may tie orassociate a host controller to a reservation held by another hostcontroller. It may be noted that reservations and I/O commands includinghost identifiers of host controllers that are associated with or tied toa reservation held by another host controller may be denied.

In implementations where logical unit of storage 352A represents thetotal usable storage capacity of the NV memory 356, a reservation heldfor storage array controller 110A, is a reservation to the entirestorage drive 171D on behalf of the storage array controller 110A,rather than storage array controller 110B.

In implementations, where storage array controller 110C and 110D hold areservation for storage array controller 110A and the reservation isassociated with storage array controller 110B, storage array controller110C and 110D may receive additional reservation commands from storagearray controller 110B. In one implementation, storage array controller110C may receive from storage array controller 110B reservation 336A.Reservation 336A may be a reservation command to acquire access (e.g.,the same access as storage array controller 110A has been granted) tostorage drive 171D. Reservation 336A may include a different hostidentifier that identifies storage array controller 110B. Storage arraycontroller 110C may identify the storage array controller 110B using thehost identifier in reservation 336A. Storage array controller 110A maydetermine that a reservation is being held for storage array controller110A and the reservation is associated with storage array controller110B using reservation status information, and deny the reservation bystorage array controller 110B.

In implementations, where storage array controller 110C and 110D hold areservation for storage array controller 110A and the reservation isassociated with storage array controller 110B, storage drive 171C mayreceive I/O commands from storage array controller 110B. In oneimplementation, storage array controller 110C may receive from storagearray controller 110B an I/O command (e.g., write command). The I/Ocommand may include a host identifier that identifies storage arraycontroller 110B. After receiving the I/O command, storage arraycontroller 110B may compare the host identifier with the reservationstatus information. Storage array controller 110C may determine that areservation is being held for storage array controller 110A and thereservation is associated with storage array controller 110B, andprevent the command from being send to storage drive 171 (e.g. drivecontroller 373A).

In implementations, where storage array controller 110C and 110D hold areservation on behalf of storage array controller 110A and thereservation is associated with storage array controller 110B, storagearray controller 110C may receive I/O commands from storage arraycontroller 110A. In one implementation, storage array controller 110Cmay receive from storage array controller 110A, an I/O command (e.g.,write command). The I/O command may include a host identifier thatidentifies storage array controller 110A. After receiving the I/Ocommand, storage array controller 110C may determine that thereservation that is being held for storage array controller 110A matchesthe host identifier in the I/O command. Responsive to determining theI/O command is requested by a host controller that holds thereservation, storage array controller 110C may pass the I/O command todrive controller 373A. Drive controller 373A may perform the I/O actionspecified in the I/O command. It may be noted that storage arraycontroller 110C may translate the I/O command into another protocol,such as a non-fabric-based protocol.

FIG. 8 illustrates an example system for managing reservations usingsubmission queues, in accordance with some implementations. Inimplementations, system 800 illustrated in FIG. 8 may be similar to andinclude similar elements as system 100 described with respect to FIG. 1, system 300 described with respect to FIG. 3 , and system 600 describedwith respect to FIG. 6 . Some elements of system 100, 300, and 600 havebeen included for purposes of illustration, rather than limitation.Other elements of system 100, 300, and 600 have not been included so asnot to obscure the implementation, rather than for limitation. It may benoted that operations described with respect to system 300 and 600, mayalso be performed using system 800 even if not explicitly described. Itmay be noted that system 800 may include the same, more, or fewerelements configured in the same or different manner in otherimplementations. For purposes of illustration, rather than limitation,in system 800 storage array controller 110A is the primary controller(e.g., primary host controller), storage array controller 110B is thesecondary controller (e.g., secondary host controller in the multi-hoststorage system), and storage array controller 110C and 110D are storageprocessor modules (e.g., storage controller). It may be noted that inother implementations, storage array controllers 110 may have differentstatuses or functions. For purposes of illustration, rather thanlimitation, in system 800 persistent storage resource 170B is shown witha single storage drive 171D. In implementations, persistent storageresource 170B may include multiple storage drives 171 with similarfeatures as described with respect to storage drive 171D. It may also benoted the operations described with respect to storage drive 171D, maybe performed in a similar manner for and by additional storage drives.

In implementations, one or more submission queues, such as submissionqueues 870, may be created for storage drive 171D. In implementations,submission queues 870 may conform to the NVMe standard. Submission queuecommands (e.g., I/O commands) may be placed into a submission queue 870,by storage array controller 110C and 110D, for example. Multiplesubmission queues 870 may be created. In implementations, the number ofsubmission queues 870 may the same or greater than the number of hostcontrollers. Submission queue commands may include identifiers such as asubmission queue identifier (SQUID), a command identifier (CMID), and aport identifier (PID). It may be noted that the following descriptionmay describe implementations using the submission queue identifier, forpurposes of illustration rather than limitation. It may also be notedthat other submission queue command identifiers may also be implementedin a similar matter, even if not explicitly described.

In implementations, storage array controller 110A and 110B sendreservations 334 and 336, respectively, to another storage array, suchas storage array 102B. Reservations 334 and 336 may be requests orcommands that allow two or more host controllers (e.g., storage arraycontroller 110A and 110B) to coordinate access (e.g., read access, writeaccess, erase access, etc.) to a storage drive, such as storage drive171D. In implementations, reservations 334A and 334B may include a hostidentifier that identifies storage array controller 110A.

In implementations, after a reservation is received by storage arraycontroller 110C and 110D, reservation proxy 342 may translate or modifythe received reservation. For the sake of illustration, rather thanlimitation, the flow of reservation 334A through system 300 will bedescribed. It may be noted that other elements receiving reservationsother than reservation 334A may perform similar operations. Inimplementations, reservation 334A includes a host identifier thatidentifies a sending host controller, such as storage array controller110A Reservation proxy 342A of storage array controller 110C may modifyreservation 334A by changing the host identifier to submission queueidentifier that is associated with a particular storage arraycontroller, such as storage array controller 110A. The submission queueidentifier may identify the particular submission queue 870A or 870Bthat is associated with a particular host controller.

For example, storage array controller 110C may modify reservation 334Ahaving a host identifier identifying storage array controller 110A witha submission queue identifier identifying logical unit of storage 352A.Similarly, storage array controller 110C may modify reservation 336Ahaving a host identifier identifying storage array controller 110B witha submission queue identifier identifying logical unit of storage 352B.Storage array controller 110C may use a table, common logic, orotherwise, to reference the received host identifier with the associatedsubmission queue identifier.

In implementations, storage array controller 110C may also translatereservation 334A from a first protocol (e.g., fabric-based protocol) toanother protocol (e.g., non-fabric protocol). In implementations, amodified reservation may refer to a reservation where at least the hostidentifier has been replaced with the associated submission queueidentifier. In other implementations, a modified reservation may referto a reservation where the host identifier has been replaced with theassociated submission queue identifier and the reservation has beentranslated consistent with another communication standard.

In implementations, the storage array controller 110C sends the modifiedreservation 334A to storage drive 171D via port 372A. The modifiedreservation 334A includes a submission queue identifier that identifiessubmission queue 870A. The modified reservation 334A is passed to drivecontroller 373A. Reservation arbiter 344A of drive controller 373A,responsive to receiving the modified reservation 334A, checks currentreservations for access to submission queue 870A. If no otherreservations are held for submission queue 870A and no otherreservations are held for submission queue 870B that are associated withsubmission queue 870A, reservation arbiter 344 may grant and hold thereservation for submission queue 870A based on the modified reservation334A. In implementations, reservation arbiter 344 may associate or tiethe reservation for submission queue 870A to another submission queue,such as submission queue 870B. It may be noted that without tying thesubmission queue 870B to the reservation for the submission queue 870A,in some implementations a host controller may still be able to accesssubmission queue 870B. A reservation held for submission queue 870A andassociated with submission queue 870B, allows storage drive 171D togrant access to logical unit of storage 352A in response to ansubmission queue command that includes a submission queue identifier toidentify submission queue 870A, and deny access to logical unit ofstorage 352A in response to an submission queue command that includes asubmission queue identifier of submission queue 870B. A reservation heldfor submission queue 870A and associated with submission queue 870B, isa reservation to the storage drive on behalf of the storage arraycontroller 110A, rather than storage array controller 110B. It may benoted that reservations and I/O commands including submission queueidentifiers of submission queues that are associated with or tied to areservation held by another submission queue may be denied. Inimplementations where logical unit of storage 352A represents the totalusable storage capacity of the NV memory 356, a reservation held forsubmission queue 870A and associated with submission queue 870B, is areservation to the entire storage drive 171D on behalf of the storagearray controller 110A, rather than storage array controller 110B.

It may also be noted that drive controller 373A and drive controller373B may communicate directly or through another component, such acommon logic block, to coordinate the arbitration of reservations andI/O commands. For example, to determine if a reservation has beengranted for submission queue 870A and associated with submission queue870B, drive controllers 373 (responsive to receiving subsequentreservations or submission queue commands) may access a common logicblock that keeps track of the current reservation.

In implementations, where storage drive 171D holds a reservation onbehalf of storage array controller 110A (e.g., a reservation forsubmission queue 870A that is tied to submission queue 870B and withoutdirect knowledge the reservation is on behalf of storage arraycontroller 110A), storage drive 171D may receive additional reservationcommands from storage array controller 110B (via storage arraycontroller 110C or 110D). In one implementation, storage arraycontroller 110C may receive from storage array controller 110Breservation 336A. Reservation 336A may be a reservation command toacquire access (e.g., the same access as storage array controller 110Ahas been granted) to storage drive 171D. Reservation 336A may include adifferent host identifier that identifies storage array controller 110B.Storage array controller 110C may determine the association between thehost identifier in the reservation 336A and the appropriate submissionqueue identifier. Storage array controller 110C may modify reservation336A to replace the host identifier identifying storage array controller110B with a submission queue identifier that identifies submission queue870B (that is associated with storage array controller 110B by storagearray controller 110C). Storage array controller 110C may send themodified reservation 336A to drive controller 373A via port 372A. Afterreceiving the modified reservation 336A, drive controller 373A mayidentify submission queue 870B using the virtual function identifier inmodified reservation 336A. Storage array controller 110A may determinethat a reservation is being held for submission queue 870A and thereservation is associated with submission queue 870B, and deny thereservation for submission queue 870B.

In implementations, where storage drive 171D holds a reservation onbehalf of storage array controller 110A (e.g., a reservation submissionqueue 870A that is tied to submission queue 870B), storage drive 171Dmay receive I/O command from storage array controller 110B. In oneimplementation, storage array controller 110C may receive from storagearray controller 110B an I/O command (e.g., write command). The I/Ocommand may include a host identifier that identifies storage arraycontroller 110B. Storage array controller 110A may determine theassociation between the host identifier in the I/O command and theappropriate submission queue identifier. Storage array controller 110Cmay modify the I/O command to replace the host identifier identifyingstorage array controller 110B with a submission queue identifier thatidentifies logical unit of storage 352B, and change the format of theI/O command into a submission queue command. Storage array controller110C may send the modified submission queue command to drive controller373A via port 372A. After receiving the modified submission queuecommand, drive controller 373A may identify submission queue 870B usingthe submission queue identifier in modified submission queue command.Storage array controller 110A may determine that a reservation is beingheld for submission queue 870A and the reservation is associated withsubmission queue 870B, and deny the execution of the I/O action based onthe modified submission queue command.

In implementations, where storage drive 171D holds a reservation onbehalf of storage array controller 110A (e.g., a reservation forsubmission queue 870A that is tied to submission queue 870B), storagedrive 171D may receive I/O commands from storage array controller 110A.In one implementation, storage array controller 110C may receive fromstorage array controller 110A, an I/O command (e.g., write command). TheI/O command may include a host identifier that identifies storage arraycontroller 110A. Storage array controller 110A may determine theassociation between the host identifier in the I/O command and theappropriate submission queue identifier. Storage array controller 110Cmay modify the I/O command to replace the host identifier identifyingstorage array controller 110A with a submission queue identifier thatidentifies submission queue 870A. Storage array controller 110C may sendthe modified submission queue command to drive controller 373A via port372A. After receiving the modified submission queue command, drivecontroller 373A may identify submission queue 870A using the submissionqueue identifier in modified submission queue command. Storage arraycontroller 110A may determine that the reservation is being held forsubmission queue 870A and that the reservation is associated withsubmission queue 870B, and matches the submission queue 870A identifiedin the modified submission queue command. Drive controller 373A mayperform the I/O action specified in the modified submission queue 870command. It may be noted that communications sent from drive controller373 to storage array controller 110C and 110D may include submissionqueue identifiers that correspond to the granted reservation, andstorage array controller 110C and 110D may modify the communication byreplacing the submission queue identifier with the appropriate hostidentifier before sending the modified communication to storage arraycontroller 110A and 110B.

In some embodiments where reservation arbitration or I/O commandarbitration is performed at the storage drive 373, for example, storagedrive 171 may reject I/O commands on a port (e.g., port 372B) with astatus indicating that an I/O action is currently not allowed on theport. In implementations, drive controller 373 may reject I/O commandson a port pursuant to some logic. For instance, drive controller 373Amay proceed to reject I/O commands on port 372B in response to grantinga reservation 334A.

FIG. 9 depicts an example computer system 900 which can perform any oneor more of the methods described herein. The computer system may beconnected (e.g., networked) to other computer systems in a LAN, anintranet, an extranet, or the Internet. The computer system may operatein the capacity of a server in a client-server network environment. Thecomputer system may be a personal computer (PC), a server, a networkrouter, switch or bridge, a storage system, or any device capable ofexecuting a set of instructions (sequential or otherwise) that specifyactions to be taken by that device. Further, while only a singlecomputer system is illustrated, the term “computer” shall also be takento include any collection of computers that individually or jointlyexecute a set (or multiple sets) of instructions to perform any one ormore of the methods discussed herein.

The exemplary computer system 900 includes a processing device 902, amain memory 904 (e.g., read-only memory (ROM), flash memory, dynamicrandom access memory (DRAM) such as synchronous DRAM (SDRAM)), asolid-state non-volatile memory 906 (e.g., flash memory, 3D crosspointmemory, magnetoresistive random-access memory (MRAM), or any other suchstorage media that does not use a physical disk), and a data storagedevice 918, which communicate with each other via a bus 930.

Processing device 902 represents one or more general-purpose processingdevices such as a microprocessor, central processing unit, or the like.In implementations, processing device 902 may be one or more or storagearray controller 110A, 110B, 110C, or 100D, drive controller 373A or373B, or other components described herein. More particularly, theprocessing device 902 may be a complex instruction set computing (CISC)microprocessor, reduced instruction set computing (RISC) microprocessor,very long instruction word (VLIW) microprocessor, or a processorimplementing other instruction sets or processors implementing acombination of instruction sets. The processing device 902 may also beone or more special-purpose processing devices such as an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA), a digital signal processor (DSP), network processor, or thelike. The processing device 902 is configured to execute a reserver 340,reservation proxy 342, or reservation arbiter 344 for performing any ofoperations discussed herein. The computer system 900 may further includea network interface device 922. The data storage device 918 may includea computer-readable storage medium 924 on which is stored reserver 340,reservation proxy 342, or reservation arbiter 344 embodying any one ormore of the methodologies or functions described herein. The reserver340, reservation proxy 342, or reservation arbiter 344 may also reside,completely or at least partially, within the main memory 904 and/orwithin the processing device 902 during execution thereof by thecomputer system 900, the main memory 904 and the processing device 902also constituting computer-readable media. The reserver 340, reservationproxy 342, or reservation arbiter 344 may further be transmitted orreceived over a network via the network interface device 922.

While the computer-readable storage medium 924 is shown in theillustrative examples to be a single medium, the term “computer-readablestorage medium” (e.g., “non-transitory computer-readable storagemedium”) may be taken to include a single medium or multiple media(e.g., a centralized or distributed database, and/or associated cachesand servers) that store the one or more sets of instructions. The term“computer-readable storage medium” shall also be taken to include anymedium that is capable of storing, encoding or carrying a set ofinstructions for execution by the machine and that cause the machine toperform any one or more of the methodologies of the present disclosure.The term “computer-readable storage medium” shall accordingly be takento include, but not be limited to, solid-state memories, optical media,and magnetic media.

Although the operations of the methods herein are shown and described ina particular order, the order of the operations of each method may bealtered so that certain operations may be performed in an inverse orderor so that certain operation may be performed, at least in part,concurrently with other operations. In certain implementations,instructions or sub-operations of distinct operations may be in anintermittent and/or alternating manner.

It is to be understood that the above description is intended to beillustrative, and not restrictive. Many other implementations will beapparent to those of skill in the art upon reading and understanding theabove description. The scope of the disclosure may, therefore, bedetermined with reference to the appended claims, along with the fullscope of equivalents to which such claims are entitled.

In the above description, numerous details are set forth. It will beapparent, however, to one skilled in the art, that the presentdisclosure may be practiced without these specific details. In someinstances, well-known structures and devices are shown in block diagramform, rather than in detail, in order to avoid obscuring the presentdisclosure.

Some portions of the detailed descriptions above are presented in termsof algorithms and symbolic representations of operations on data bitswithin a computer memory. These algorithmic descriptions andrepresentations are the means used by those skilled in the dataprocessing arts to most effectively convey the substance of their workto others skilled in the art. An algorithm is here, and generally,conceived to be a self-consistent sequence of operations leading to adesired result. The operations are those requiring physicalmanipulations of physical quantities. Usually, though not necessarily,these quantities take the form of electrical or magnetic signals capableof being stored, transferred, combined, compared, and otherwisemanipulated. It has proven convenient at times, principally for reasonsof common usage, to refer to these signals as bits, values, elements,symbols, characters, terms, numbers, or the like.

It may be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise, as apparent from the followingdiscussion, it is appreciated that throughout the description,discussions utilizing terms such as “receiving,” “identifying,”“granting,” “holding,” “associating,” “modifying,” “sending,” “denying,”“determining,” “sending,” “performing,” or the like, refer to the actionand processes of a computer system, or similar electronic computingdevice, that manipulates and transforms data represented as physical(electronic) quantities within the computer system's registers andmemories into other data similarly represented as physical quantitieswithin the computer system memories or registers or other suchinformation storage, transmission or display devices.

The present disclosure also relates to an apparatus for performing theoperations herein. This apparatus may be specially constructed for therequired purposes, or it may comprise a general purpose computerselectively activated or reconfigured by a computer program stored inthe computer. Such a computer program may be stored in a computerreadable storage medium, such as, but not limited to, any type of diskincluding floppy disks, optical disks, CD-ROMs, and magnetic-opticaldisks, read-only memories (ROMs), random access memories (RAMs), EPROMs,EEPROMs, magnetic or optical cards, or any type of media suitable forstoring electronic instructions, each coupled to a computer system bus.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other apparatus. Various general purposesystems may be used with programs in accordance with the teachingsherein, or it may prove convenient to construct more specializedapparatus to perform the required method operations. The requiredstructure for a variety of these systems will appear as set forth in thedescription below. In addition, the present disclosure is not describedwith reference to any particular programming language. It will beappreciated that a variety of programming languages may be used toimplement the teachings of the disclosure as described herein.

The present disclosure may be provided as a computer program product, orsoftware, that may include a machine-readable storage medium havingstored thereon instructions, which may be used to program a computersystem (or other electronic devices) to perform a process according tothe present disclosure. A machine-readable storage medium includes anymethod for storing or transmitting information in a form readable by amachine (e.g., a computer). For example, a machine-readable (e.g.,computer-readable) medium includes a machine (e.g., a computer) readablestorage medium (e.g., read only memory (“ROM”), random access memory(“RAM”), magnetic disk storage media, optical storage media, flashmemory devices, etc.).

The words “example” or “exemplary” are used herein to mean serving as anexample, instance, or illustration. Any aspect or design describedherein as “example” or “exemplary” is not necessarily to be construed aspreferred or advantageous over other aspects or designs. Rather, use ofthe words “example” or “exemplary” is intended to present concepts in aconcrete fashion. As used in this application, the term “or” is intendedto mean an inclusive “or” rather than an exclusive “or”. That is, unlessspecified otherwise, or clear from context, “X includes A or B” isintended to mean any of the natural inclusive permutations. That is, ifX includes A; X includes B; or X includes both A and B, then “X includesA or B” is satisfied under any of the foregoing instances. In addition,the articles “a” and “an” as used in this application and the appendedclaims may generally be construed to mean “one or more” unless specifiedotherwise or clear from context to be directed to a singular form.Moreover, use of the term “an implementation” or “one implementation” or“an implementation” or “one implementation” throughout is not intendedto mean the same implementation or implementation unless described assuch. Furthermore, the terms “first,” “second,” “third,” “fourth,” etc.as used herein are meant as labels to distinguish among differentelements and may not necessarily have an ordinal meaning according totheir numerical designation.

What is claimed is:
 1. A method comprising: responsive to receiving amodified first reservation command from a storage controller,identifying, by a storage drive, a first range of storage based on afirst range identifier of the modified reservation command, the modifiedfirst reservation command generated by replacing a first host identifierwith the first range identifier; and granting, by the storage drive, areservation for access to the storage drive on behalf of a first hostcontroller by associating the reservation for the first range with asecond range of storage.
 2. The method of claim 1, wherein the firstrange is a first namespace and the first range identifier is a firstnamespace identifier that identifies a first namespace for the firstrange of storage of the storage drive.
 3. The method of claim 1, whereingranting, by the storage drive, the reservation to the access to thestorage drive by associating the reservation for the first range with asecond range of storage, further comprises: holding, by the storagedrive, the reservation for the first range of storage of the storagedrive based on the first reservation comprising the first rangeidentifier; and associating, by the storage drive, a second range ofstorage of the storage drive with the reservation held for the firstrange of storage.
 4. The method of claim 3, wherein granting, by thestorage drive, the reservation to the access to the storage drive byassociating the reservation for the first range with a second range ofstorage, further comprises granting, by the storage drive, access to thefirst range of storage and the second range of storage of the storagedrive on behalf of the first host controller, rather than a second hostcontroller, based on the reservation for the first range.
 5. The methodof claim 4, further comprising: modifying, by the storage drive, asecond reservation command comprising a second host identifier toidentify the second host controller by replacing the second hostidentifier with a second range identifier that is associated with thesecond host controller and that identifies a second range of storage ofthe storage drive; and sending the modified second reservation commandcomprising the second range identifier to the storage drive.
 6. Themethod of claim 5, further comprising, responsive to receiving themodified second reservation command, denying a reservation made usingthe modified second reservation command based on the reservation heldfor the first range.
 7. The method of claim 1, wherein the access to thestorage drive comprises a write access, a read access, or a read-writeaccess.
 8. The method of claim 1, wherein the first reservation commandis compatible with a Nonvolatile Memory Express (NVMe) over Fabricsstandard, and the modified first reservation command is compatible witha NVMe standard.
 9. The method of claim 1, wherein a second rangeidentifier is a second namespace identifier that identifies a secondnamespace that is the second range of storage of the storage drive. 10.The method of claim 2, wherein the first range and the second rangerepresent a same physical storage of the storage drive.
 11. A multi-hoststorage system comprising a memory; a storage controller,communicatively coupled to the memory, to: receive, from a first hostcontroller of the multi-host storage system, a first reservation commandto acquire access to a storage drive that is shared to a second hostcontroller of the multi-host storage system, the reservation commandcomprising a first host identifier to identify the first hostcontroller; modify the first reservation command by replacing the firsthost identifier with a first range identifier that is associated withthe first host controller and that identifies a first range of storageof the storage drive; and send the modified first reservation commandcomprising the first range identifier to a drive controller of thestorage drive.
 12. The multi-host storage system of claim 11, thestorage controller further to: receive, from the second host controller,a second reservation command to acquire the access to the storage drive,the reservation command comprising a second host identifier to identifythe second host controller; modify the second reservation command byreplacing the second host identifier with a second range identifier thatis associated with the second host controller and that identifies asecond range of storage of the storage drive; and send the modifiedsecond reservation command comprising the second range identifier to thedrive controller of the storage drive.
 13. The multi-host storage systemof claim 11, wherein the access to the storage drive comprises a writeaccess, a read access, or a read-write access.
 14. The multi-hoststorage system of claim 11, wherein the first reservation command iscompatible with a Nonvolatile Memory Express (NVMe) over Fabricsstandard, and the modified first reservation command is compatible witha NVMe standard.
 15. A non-transitory computer-readable mediumcomprising instructions that, when executed by a multi-host storagesystem, cause the multi-host storage system to: receive, by a storagedrive of the multi-host storage system, a modified first submissionqueue command comprising a first range identifier, the modified firstsubmission queue command generated by replacing a first host identifierwith the first range identifier; responsive to receiving the modifiedfirst submission queue command, identify, by the storage drive, a firstrange of storage based on the first range identifier of the modifiedsubmission queue command; and grant, by the storage drive, a reservationfor access to the storage drive on behalf of the first host controllerby associating the reservation for the first range with a second rangeof storage.
 16. The non-transitory computer-readable medium of claim 15,wherein the submission queue command is an I/O command.
 17. Thenon-transitory computer-readable medium of claim 16, wherein the I/Ocommand is a write command.
 18. The non-transitory computer-readablemedium of claim 15, wherein the I/O command is a read command.
 19. Thenon-transitory computer-readable medium of claim 15, wherein the I/Ocommand is a flush command.
 20. The non-transitory computer-readablemedium of claim 15, wherein the flush command is configured to move datato the storage drive.